High data low latency communications with minimized power consumption

ABSTRACT

A data collection device capable of communicating with an endpoint device over a network comprises a first communication means for low data rate messaging, a second communication means for high data rate messaging, and a controller configured to send a wake-up command including a request for data to the endpoint device at a low data rate via the first communication means, the wake-up command requiring the requested data to be transmitted at a high data rate, and receive the requested data from the endpoint device at the high data rate via the second communication means. When transmission via a high data rate is not required, data may be transmitted to the data collection device at the low data rate via the first communication means. The wake-up command may involve a regularly scheduled request for data, an unscheduled request for data, and/or an alarm event. Various methodologies are also disclosed.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of, and claims priority to, U.S.patent application Ser. No. 14/969,137, filed on Dec. 15, 2015, andentitled “High Data Low Latency Communications with Minimized PowerConsumption,” which is incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

This disclosure relates generally to communication systems, and, moreparticularly, to communication systems involving battery operateddevices.

BACKGROUND

The demands on data collection systems have grown significantly inrecent years as technology continues to improve and the need for moreinformation continues to increase. Some data collection systems, such asutility metering systems and other systems that require collection oflarge amounts of data from a large number of endpoints, are primarilywireless systems with many, if not all, of the endpoints powered bybatteries. In utility metering systems (in particular, gas and/or watermetering systems), this may be for safety reasons, as it is notconsidered safe to run electricity near gas or water. The communicationnetworks used for these systems are typically low data-rate networksthat until recently served the purpose well. However, combining a needfor low latency and even higher amounts of data over a low data-ratenetwork will require more power, and in turn will require much stronger,and/or a higher number of, batteries per endpoint. Otherwise, thebattery life of an endpoint will not meet the current lifetimerequirement of about 10-20 years. Cellular networks may have thecapability of handling data transfers at high data rates, but usingcellular communications consumes a large amount of power in theendpoints, especially with continuous use. In turn, using cellularcommunications may limit responses to possible alarm messages sinceendpoints cannot be connected to the cellular network continuously, oreven for extended periods of time, without significant drain on power.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of a network environment in which examplemethods, apparatus, and articles of manufacture disclosed herein may beimplemented, according to embodiments of this disclosure.

FIG. 2 is a sequence diagram illustrating communications between a datacollection device (e.g., of a head-end system), and an endpoint,according to embodiments of this disclosure.

FIG. 3 is a flow diagram of an example communication process from theperspective of an endpoint device, according to embodiments of thisdisclosure.

FIGS. 4 and 5 are flow diagrams of example communication processes fromthe perspective of a data collection device, according to embodiments ofthis disclosure.

FIG. 6 is a block diagram of an example processing system that mayembody an endpoint device or data collection device, according toembodiments of the present disclosure.

In the drawings, the leftmost digit(s) of a reference number mayidentify the drawing in which the reference number first appears.

DETAILED DESCRIPTION

Current communication systems used in data collection networks may beimplemented for specific operations (e.g., involving wirelesscommunications to/from battery-operated devices), which may work forfixed networks, but may be short in range and very slow (i.e.,transferring data at a low data-rate (e.g., less than 10 Kbps)). Inaddition, due to power considerations, endpoints in these systems cannotbe left on very long, so access to these devices may be limited. Thesecurrent solutions are not sufficient for systems that require quick, lowlatency retrieval of large amounts of data, both scheduled andon-demand. The following description discloses communication solutionsin which scheduled and/or on-demand, low latency collection of largeamounts of data can occur over an increased range while minimizing powerconsumption.

Embodiments are now described with reference to the figures, where likereference numbers may indicate identical or functionally similarelements. While specific configurations and arrangements are discussed,it should be understood that this is done for illustrative purposesonly. A person skilled in the relevant art will recognize that otherconfigurations and arrangements can be used without departing from thespirit and scope of the description. It will be apparent to a personskilled in the relevant art that this can also be employed in a varietyof other systems and applications other than what is described herein.

FIG. 1 illustrates an example data collection network 100 (e.g., anadvanced meter reading (AMR) network or other similar network). Thenetwork 100 may include a central office 102, which may be associatedwith a data collection/processing entity (e.g., a utility company in thecase of an AMR network). The central office may communicate with networknodes through one or more networks 104, which may be the Internet orother network having widespread or local functionality. Network nodesmay include nodes 106-114, which may include, for example, endpointdevices such as utility meters or other devices that may comprisesensors, actuators, etc. The plurality of network nodes/devices 106-114may be configured in a mesh network, star network or otherconfiguration. One or more of the network nodes (e.g., device 106) maybe a data collector and/or concentrator that may be configured forcommunication (e.g., radio frequency (RF) communication, cellularcommunication, etc.) with a plurality of downstream devices 108-114,which may also be configured for similar communications. In an exampleoperation, data collector 106 may receive data or other communicationsfrom endpoint devices 108-114. For example, for an AMR network, the datamay include consumption information associated with an electric, gas orwater meter. Additionally, data collector 106 may send software updates,firmware updates, instructions or other information to one or more ofthe endpoint devices 108-114. While in this example, a data collector isshown as a network node, in other embodiments, the data collector may belocated at the central office (e.g., data collector 116) and/or may beembodied in a mobile data collection device (not shown). In anembodiment, one or more network nodes (e.g., endpoint devices 106-114)may be battery-operated devices.

In an expanded view, data collector 116 (and/or data collector 106) mayinclude, among other components, a controller 120, a memory 122, a lowdata rate communication subsystem 124 (e.g., configured for RFcommunications or another type capable of low data rate communications(e.g., less than 10 Kbps)), and a high data rate communication subsystem126 (e.g., configured for cellular communications (e.g., 3G, 4G, LTE,LTE Direct, LTE Advanced, LTE-U, etc.), Wi-Fi, WiMAX, or any otherstandards-based or proprietary communications system capable of highdata rate communications (e.g., greater than 1 Mbps)). Similarly, anendpoint device, such as any of devices 108-114 (and 106, if notconfigured as a data collector), may include, among other components, acontroller 130, a memory 132, a low data rate communication subsystem134 (e.g., configured for RF communications or another type capable oflow data rate communications (e.g., less than 10 Kbps)), and a high datarate communication subsystem 136 (e.g., configured for cellularcommunications (e.g., 3G, 4G, LTE, LTE Direct, LTE Advanced, LTE-U,etc.), Wi-Fi, WiMAX, any other standards-based or proprietarycommunications system capable of high data rate communications (e.g.,greater than 1 Mbps)).

FIG. 2 is a sequence diagram illustrating communications between a datacollection device and an endpoint device, according to embodiments ofthis disclosure. As shown in FIG. 2, a data collection device 216 (e.g.,device 116 of central office 102, or device 106 of FIG. 1 (if configuredas a data collector)) may include a low data rate (LDR) communicationsubsystem 224 and a high data rate (HDR) communication subsystem 226. Anendpoint device 208 (e.g., example endpoint device 108 of FIG. 1) mayinclude a low data rate (LDR) communication subsystem 234 and a highdata rate (HDR) communication subsystem 236. For regularly scheduleddata transfers, endpoint device 208 may initiate its HDR communicationsubsystem 236 (at 242), send the data to data collection device 216 atthe high data rate (at 244), and power off the HDR communicationsubsystem 236 (at 246) to conserve power. In embodiments, initiating theHDR communication subsystem 236 may be in response to an internalcommand within endpoint device 208 (e.g., to turn on at a scheduled timeor during a scheduled time window), or may be in response to a “wake up”command received from data collection device 216 (not shown). In anembodiment, HDR communication subsystem 236 may need to be registeredwith an associated network (e.g., one or more of network(s) 104 ofFIG. 1) upon initiation.

For unscheduled data transfer requests and/or other requests, if LDRcommunication subsystem 234 is not already on, at 252, endpoint device208 may initiate LDR communication subsystem 234 (which may includeregistration with an associated network, if necessary). In embodiments,initiating the LDR communication subsystem 234 may be in response to aninternal command within endpoint device 208 (e.g., to turn on at ascheduled time or during a scheduled time window), or may be in responseto a “wake up” command (not shown) received from data collection device216. At 254, LDR communication subsystem 234 may wait, or listen, for acommand. At 256, a command from data collection device 216 may bereceived by endpoint device 208 at a low data rate via LDR communicationsubsystems 224/234. In an embodiment, endpoint device 208 may internallyissue a command (e.g., in response to an alarm event occurring at theendpoint device). The command may be, for example, an unscheduled datatransfer, a parameter change for the endpoint device, etc. The receivedcommand, if sent by data collection device 216, may be in response to,for example, a customer complaint (e.g., regarding a bill), a need forgeneral investigation or auditing of an endpoint device, or an alarmevent received by data collection device 216. An alarm event may be analert regarding, for example, an over-pressure condition, anunder-pressure condition, or an over-consumption condition at endpointdevice 208, or at a neighboring (or nearby) endpoint device to endpointdevice 208. Neighboring, or groups of, endpoints may be polled for datafor investigative purposes, for example.

In embodiments, whether a data transfer at a high data rate is requiredmay be determinable by the endpoint device. For example, the endpointdevice may be instructed to transfer data and/or a response in thereceived command/request. In another example, whether to transfer dataand/or a response using a high data rate may be determined based on howmuch data is to be transferred (e.g., based on a predetermined thresholdamount) and/or based on the urgency of the command/request (e.g., if inresponse to an alarm event involving a potentially dangerous condition).In an embodiment, if the command/request received at endpoint device 208does not require a data transfer at a high data rate, a response to thecommand/request may be sent from endpoint device 208 at a low data ratevia LDR communication subsystems 224/234 (258). The response at the lowdata rate may include, for example, requested data (e.g., if a smallamount or not urgently needed), and/or a confirmation whether therequest was received and/or executed (e.g., a successful parameterchange, an error message, etc.). If, however, the command/requestreceived at endpoint device 208 does require a data transfer at a highdata rate, HDR communication subsystem 236 may be initiated (260) byendpoint device 208 (e.g., a receiver of the HDR communication subsystem236 of endpoint device 208 may be turned on). In an embodiment, therequest received, if from data collection device 216, may include acommand to the endpoint device to “wake up” or turn on the HDRcommunication subsystem 236. In another embodiment, the endpoint device208 itself may send an instruction to “wake up” or turn on the HDRcommunication subsystem 236 in response to receiving the request. Ifnecessary, HDR communication subsystem 236 may be registered with itsassociated network as part of its initiation. At 262, a response may besent from endpoint device 208 to data collection device 216 via the HDRcommunication subsystems 226/236. The response may include for example,requested data, and/or a confirmation whether the request was receivedand/or executed (e.g., a successful parameter change, an error message,etc.). Once the transmission at a high data rate is complete, HDRcommunication subsystem 236 at endpoint device 208 may be turned off(264) to conserve power. The LDR communication subsystem 234 mayoptionally be turned off as well.

FIG. 3 is a flow diagram of an example communication process 300 fromthe perspective of an endpoint device (such as any of endpoint devices106-114), according to embodiments of this disclosure. At 302, if not onalready, a receiver of a first communication subsystem (e.g., low datarate communication subsystem 134 of FIG. 1) of the endpoint device,which is capable of low data rate communications, may be turned on by acontroller (e.g., controller 130) of the endpoint device. In anembodiment, a data collector (e.g., data collection device 116 of ahead-end system, or device 106 (if a data collector)) may have sent acommand to the endpoint device to “wake up” and/or to turn on the lowdata rate communication subsystem. In another embodiment, the endpointdevice itself may send an instruction to “wake up” or turn on the lowdata rate communication subsystem (e.g., at a predetermined “wake up”time, during a predetermined “wake up” window during which the endpointdevice is scheduled to be on and listening for communications, inresponse to an alarm event received or detected by the endpoint device,etc.). At 304, the endpoint device may listen, or wait, for a commandfrom data collection device 116 (or 106), or internally (e.g., inresponse to an alarm event). At 306, a command may be received from thedata collection device 116 (or 106), or may be issued/receivedinternally. The received command may be, for example, a request for aregularly scheduled submission of data, an unscheduled request for data,a parameter change request for the endpoint device, etc. The receivedwake-up command and/or the command requesting data or a parameter changemay have been sent in response to, for example, a customer complaint(e.g., regarding a bill), a need for general investigation or auditingof an endpoint device, or an alarm event received by the data collectiondevice 116 (or 106) or by the endpoint itself. An alarm event may be analert regarding, for example, an over-pressure condition, anunder-pressure condition, or an over-consumption condition at theendpoint device, or at a neighboring (or nearby) endpoint device.

At 308, the endpoint device may determine whether the command requiresdata transmission at a high data rate (e.g., if a large amount of datais requested, if data is requested in response to an alarm condition(e.g., a potentially dangerous condition or one needing immediateinvestigation, etc.), etc.). If data transmission at a high data rate isnot needed (e.g., if only a small amount of data is requested, or if therequest was for a parameter change, and not urgently needed, etc.), therequested data and/or a response may be sent to data collection device116 (or 106) at the low data rate via the low data rate communicationsubsystem at 310. The response may include requested data, and/or mayconfirm that the request was received and/or executed (e.g., asuccessful parameter change). A response may also signify if the requestwas unable to be executed (e.g., an error message). If data transmissionat a high data rate is needed, a receiver of a high data ratecommunication subsystem of the endpoint device (e.g., high data ratecommunication subsystem 136), capable of data transmission at a highdata rate, may be turned on at 312. In an embodiment, the requestreceived from data collection device 116 (or 106) may have included acommand to the endpoint device to “wake up” or turn on the high datarate communication subsystem. In another embodiment, the endpoint deviceitself may send an instruction to “wake up” or turn on the high datarate communication subsystem in response to receiving the request. Ifnecessary, the high data rate communication subsystem may be registeredwith its associated network(s) at 314. At 316, the requested data and/ora response may be sent to data collection device 116 (or 106) at thehigh data rate via the high data rate communication subsystem. Theresponse may include requested data, and/or may confirm that the requestwas received and/or executed. A response may also signify if the requestwas unable to be executed (e.g., an error message). Once thetransmission at a high data rate is complete, the high data ratecommunication subsystem may be turned off to conserve power. The lowdata rate communication subsystem may optionally be turned off as well.

FIGS. 4 and 5 are flow diagrams of example communication processes400/500 from the perspective of a data collection device (e.g., datacollector 116, or 106), according to embodiments of this disclosure. Inprocess 400, the high data rate is used for all requested datatransfers, whereas, in process 500, the high data rate is not usedunless required. Referring to process 400, at 402, a data requestcommand may be sent to an endpoint device (e.g., any of devices 106-114)at a low data rate via a first communication subsystem (e.g., low datarate communication subsystem 124, such as an RF communications system).The request for data may also include a “wake up” command, if, forexample, the request is being sent outside of that endpoint's scheduled“on” time. At 404, requested data is received from the endpoint deviceat a high data rate via a second communication subsystem (e.g., highdata rate communication subsystem 126, such as a cellular communicationssystem). Optionally, a data collector may also need data from one ormore neighboring, or nearby, endpoint devices of the endpoint device.This may be desired, for example, in an alarm or investigation situation(e.g., involving a gas or water leak, an over or under pressuresituation, etc.), which may require information from a plurality ofdevices to assist in identifying a problem. In this situation, a datacollection device may optionally (at 406), send a second data requestcommand to one or more neighboring, or nearby, endpoint device(s) of theendpoint device at the low data rate via the first communicationsubsystem, and may receive (at 408) the requested data from theneighboring, or nearby, endpoint device(s) at the high data rate via thesecond communication subsystem.

Process 500 is similar to process 400, except that the secondcommunication subsystem for communicating using the high data rate isnot used unless necessary. At 502, a data request command may be sent toan endpoint device at the low data rate, via the first communicationsubsystem. At 504, requested data is received from the endpoint deviceat the high data rate via the second communication subsystem ifcommunications via the high data rate is necessary (e.g., if there arelarge amounts of data requested, or if the information is neededimmediately in case of a potentially dangerous alarm condition, etc.).Otherwise, the requested data may be received from the endpoint deviceat the low data rate via the first communication system to conservepower (e.g., to conserve, or prolong, battery life). Similar to process400, a data collection device may optionally (at 506), send a seconddata request command to one or more neighboring, or nearby, endpointdevice(s) of the endpoint device at the low data rate via the firstcommunication subsystem, and may receive (at 508) the requested datafrom the neighboring, or nearby, endpoint device(s) at the high datarate via the second communication subsystem if necessary. Otherwise, therequested data may be received from the neighboring, or nearby, endpointdevice(s) at the low data rate via the first communication subsystem.

One or more features disclosed herein may be implemented in hardware,software, firmware, and/or combinations thereof, including discrete andintegrated circuit logic, application specific integrated circuit (ASIC)logic, and microcontrollers, and may be implemented as part of adomain-specific integrated circuit package, or a combination ofintegrated circuit packages. The terms software and firmware, as usedherein, refer to a computer program product including at least onecomputer readable medium having computer program logic, such ascomputer-executable instructions, stored therein to cause a computersystem to perform one or more features and/or combinations of featuresdisclosed herein. The computer readable medium may be transitory ornon-transitory. An example of a transitory computer readable medium maybe a digital signal transmitted over a radio frequency or over anelectrical conductor, through a local or wide area network, or through anetwork such as the Internet. An example of a non-transitory computerreadable medium may be a compact disk, a flash memory, SRAM, DRAM, ahard drive, a solid state drive, or other data storage device.

A processing platform of an endpoint device (e.g., endpoint device 108),a computing device of a head-end system (e.g., device 116), a mobilecollection device (not shown), and/or a data collection device (e.g.,device 106) may be embodied in any type of mobile and/or non-mobilecomputing device. Examples of mobile devices may include, but are not tobe limited to, laptop computers, ultra-laptop computers, tablets, touchpads, portable computers, handheld computers, palmtop computers,personal digital assistants (PDAs), e-readers, cellular telephones,combination cellular telephone/PDAs, mobile smart devices (e.g., smartphones, smart tablets, etc.), mobile internet devices (MIDs), mobilemessaging devices, mobile data communication devices, mobile mediaplaying devices, cameras, mobile gaming consoles, wearable devices,mobile industrial field devices, etc. Examples of non-mobile devices mayinclude, but are not to be limited to, servers, personal computers(PCs), Internet appliances, televisions, smart televisions, datacommunication devices, media playing devices, gaming consoles,industrial field devices, etc.

FIG. 6 is a block diagram of an example mobile or non-mobile device,according to embodiments. Processing platform 600 may include one ormore processors 682, memory 684, one or more secondary storage devices686, one or more input/output devices 688, and/or one or morecommunication interfaces 690, in communication via a bus, line, orsimilar implementation (not shown). Processing platform 600 may alsoinclude a power supply 698, which may include an interface to anelectricity source and/or may include one or more batteries.Processor(s) 682 may be implemented by, for example but not limitation,one or more integrated circuits, logic circuits, microprocessors,controllers, etc. Processor(s) 682 may include a local memory 692 (e.g.,a cache). Memory 684 may include a volatile and/or a non-volatilememory. Volatile memory may be implemented by, for example but notlimitation, Synchronous Dynamic Random Access Memory (SDRAM), DynamicRandom Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM)and/or any other type of random access memory device. Non-volatilememory may be implemented by flash memory and/or any other desired typeof memory device. Access to memory 684 may be controlled by a memorycontroller (not shown). Data stored in local memory 692 and/or memory684 may be used by processor(s) 682 to facilitate data collectionfunctions and/or communications, according to embodiments of thisdisclosure.

Input/output device(s) 688 may allow a user to interface withprocessor(s) 682. Input devices may allow a user to enter data and/orcommands for processor(s) 682. Input devices may include, for example,an audio sensor, a microphone, a camera (e.g., still, video, etc.), akeyboard, a button, a mouse, a touchscreen, a track-pad, a trackball,isopoint, a voice recognition system, etc. Output devices may provide orpresent information to a user. Output devices may include, for example,display devices (e.g., a light emitting diode (LED), an organic lightemitting diode (OLED), a liquid crystal display, a cathode ray tubedisplay (CRT), a touchscreen, a tactile output device, a printer,speakers, etc.). The input/output device(s) 688 may be connected toprocessor(s) 682, for example, with an interface circuit (not shown).The interface circuit may be implemented by any type of interfacestandard, such as, for example, an Ethernet interface, a universalserial bus (USB), a PCI express interface, etc. For use with an outputdevice, the interface circuit may include a graphics driver card, chip,and/or processor.

Communication interface(s) 690 may be implemented in hardware or acombination of hardware and software, and may provide wired or wirelessnetwork interface(s) to one or more networks, such as network(s) 104 ofFIG. 1. Communication interface(s) 690 may be a part of, or connectedwith, the interface circuit discussed above, and/or may include orconnect with communication devices such as a transmitter, a receiver, atransceiver, a modem and/or network interface card to facilitateexchange of data with external devices (e.g., computing devices of anykind) via a network, such as network(s) 104. Embodiments describedherein may include a first communication interface for low data ratecommunications (e.g., less than 10 Kbps) and a second communicationinterface for high data rate communications (e.g., greater than 1 Mbps).

Secondary storage device(s) 686 may store processing logic 694 (e.g.,software) to be executed by processor(s) 682, and/or data 696.Processing logic 694 and data 696 may be used by processor(s) 682 tofacilitate data collection functions and/or communications betweendevices, according to embodiments of this disclosure. Processing logic694 may include instructions for executing the methodology describedherein, for example. Examples of secondary storage device(s) 686 mayinclude one or more hard drive disks, compact disk (CD) drives, digitalversatile disk (DVD) drives, Blu-ray disk drives, redundant array ofindependent disks (RAID) systems, floppy disk drives, flash drives, etc.Data and/or processing logic may be stored on a removable tangiblecomputer readable storage medium (e.g., a floppy disk, a CD, a DVD, aBlu-ray disk, etc.) using one or more of the secondary storage device(s)686.

The technology disclosed herein provides scheduled and/or on-demand lowlatency collection of large amounts of data from a large number ofendpoint devices in which power consumption is minimized. In theembodiments described herein, it does not matter what information iscommunicated or what protocols or communication methods are used as longas one method can be used for higher data rate communications than othermethod(s) used. This multi-method communications solution allows for adesired high data rate without a significant power expense. Otheradvantages may also be contemplated.

The particular examples and scenarios used in this document are for easeof understanding and are not to be limiting. Though described for usewith data collection from battery-powered devices used for utilitymetering, features described herein may be used in many other contextsand situations that may or may not involve battery power or utilitymetering. The power-saving features discussed herein may be beneficialin many other systems involving communications between devices.

Although certain example methods, apparatus and articles of manufacturehave been disclosed herein, the scope of coverage of this patent is notlimited thereto. On the contrary, this patent covers all methods,apparatus and articles of manufacture fairly falling within the scope ofthe claims of this patent.

What is claimed is:
 1. A data collection device capable of communicatingwith an endpoint device over a network, the data collection devicecomprising: a first communication means configured for low data ratemessaging; a second communication means configured for high data ratemessaging; and a controller in communication with the first and secondcommunication means, wherein the controller is configured to: send awake-up command including a request for data to the endpoint device at alow data rate via the first communication means, the wake-up commandrequiring the requested data to be transmitted at a high data rate; andreceive the requested data from the endpoint device at the high datarate via the second communication means.
 2. The data collection deviceof claim 1, wherein the controller is further configured to: receivemessages from the endpoint device at the low data rate via the firstcommunication means when transmission at the high data rate is notrequired.
 3. The data collection device of claim 1, wherein thecontroller is further configured to: send a data request command to oneor more neighbor endpoint devices of the endpoint device at the low datarate via the first communication means; and receive requested data fromthe neighbor endpoint devices at the high data rate via the secondcommunication means.
 4. The data collection device of claim 3, whereinthe requested data from the neighbor endpoint devices is received at thehigh data rate via the second communication means if the high data rateis required, otherwise the requested data from the neighbor endpointdevices is received at the low data rate via the first communicationmeans.
 5. The data collection device of claim 1, wherein the firstcommunication means uses radio frequency communications.
 6. The datacollection device of claim 1, wherein the second communication meansuses at least one of cellular communications, Wi-Fi, or WiMAX.
 7. Thedata collection device of claim 1, wherein the wake-up command involvesone or more of: a regularly scheduled request for data, an unscheduledrequest for data, or an alarm event.
 8. The data collection device ofclaim 7, wherein the wake-up command is related to an alarm event at autility resource involving one or more of: an over-pressure condition,an under-pressure condition, or an over-consumption condition of theutility resource.
 9. A method of communication between a data collectiondevice and an endpoint device over a network, the method comprising:sending a wake-up command including a request for data to the endpointdevice at a low data rate via a first communication means configured forlow data rate messaging, the wake-up command requiring the requesteddata to be transmitted at a high data rate; and receiving the requesteddata from the endpoint device at the high data rate via a secondcommunication means configured for high data rate messaging.
 10. Themethod of claim 9, further comprising: receiving messages from theendpoint device at the low data rate via the first communication meanswhen transmission at the high data rate is not required.
 11. The methodof claim 9, further comprising: sending a data request command to one ormore neighbor endpoint devices of the endpoint device at the low datarate via the first communication means; and receiving requested datafrom the neighbor endpoint devices at the high data rate via the secondcommunication means.
 12. The method of claim 11, wherein the requesteddata from the neighbor endpoint devices is received at the high datarate via the second communication means if the high data rate isrequired, otherwise receiving the requested data from the neighborendpoint devices at the low data rate via the first communication means.13. The method of claim 9, wherein the wake-up command involves one ormore of: a regularly scheduled request for data, an unscheduled requestfor data, or an alarm event.
 14. The method of claim 13, wherein thewake-up command is related to an alarm event at a utility resourceinvolving one or more of: an over-pressure condition, an under-pressurecondition, or an over-consumption condition of the utility resource. 15.A non-transitory computer-readable medium having computer program logicstored thereon, the computer program logic including instructions tocause a controller of a data collection device to: send a wake-upcommand including a request for data to the endpoint device at a lowdata rate via a first communication means configured for low data ratemessaging, the wake-up command requiring the requested data to betransmitted at a high data rate; and receive the requested data from theendpoint device at the high data rate via a second communication meansconfigured for high data rate messaging.
 16. The computer readablemedium of claim 15, wherein the instructions further cause thecontroller to: receive messages from the endpoint device at the low datarate via the first communication means when transmission at the highdata rate is not required.
 17. The computer readable medium of claim 15,wherein the instructions further cause the controller to: send a datarequest command to one or more neighbor endpoint devices of the endpointdevice at the low data rate via the first communication means; andreceive requested data from the neighbor endpoint devices at the highdata rate via the second communication means.
 18. The computer readablemedium of claim 17 wherein the requested data from the neighbor endpointdevices is received at the high data rate via the second communicationmeans if the high data rate is required, otherwise receiving therequested data from the neighbor endpoint devices at the low data ratevia the first communication means.
 19. The computer readable medium ofclaim 15, wherein the wake-up command involves one or more of: aregularly scheduled request for data, an unscheduled request for data,or an alarm event.
 20. The computer readable medium of claim 19, whereinthe wake-up command is related to an alarm event at a utility resourceinvolving one or more of: an over-pressure condition, an under-pressurecondition, or an over-consumption condition of the utility resource.